\documentclass[a0paper,portrait]{a0poster}

\input{hg.id}

\usepackage{color,url,graphicx,hyperref}
\usepackage[a0paper,margin=0pt]{geometry}
                   % belt and braces options for geometry package

\usepackage[absolute]{textpos}

\usepackage{gulogo}
%\usepackage[SciEng]{gulogo}

\usepackage{ifxetex}

\ifxetex
  % I don't think this works, as I think the poster stuff is PS-specific
 \usepackage{fontspec}
  % see documentation for a0poster class for the size options here
  %\def\DarkBlue{\special{color cmyk 1.0 0.6 0.1 0.53}}
  % \def\Red{\special{color cmyk 0.0 0.7 0.7 0.0}}
  \iffalse
    \setromanfont[Numbers=OldStyle, Ligatures=Rare]{Hoefler Text}
    \setsansfont{Optima}
    \setmonofont[Scale=0.8]{Monaco}
    \def\Textsize{\normalsize \fontsize{24}{30}\rmfamily\selectfont}
    \def\small{\fontsize{18}{18}\selectfont}
    \def\LHead#1{\noindent{\special{color push}%
        \fontsize{36}{40}\rmfamily\DarkBlue #1%
        \special{color pop}}\smallskip}
    \def\Title#1{\noindent{\special{color push}
        \fontsize{60}{60}\rmfamily\Red #1%
        \special{color pop}}}
  \else
    \setromanfont{Helvetica Neue}
    \setsansfont{Helvetica Neue}
    \setmonofont[Scale=0.8]{Monaco}
    \def\Textsize{\normalsize \fontsize{26}{32}\rmfamily\selectfont}
    \def\small{\fontsize{18}{18}\selectfont}
    \def\LHead#1{\noindent\textcolor{unicolour}{\fontsize{36}{40}\rmfamily #1}\par\smallskip}
    %\def\Title#1{\noindent\textcolor{csecolour}{\fontsize{64}{64}\rmfamily #1}}
    \def\Title#1{\noindent\textcolor{csecolour}{\fontsize{72}{72}\rmfamily #1}}
  \fi
\else
  \usepackage{times} % fiddle with fonts?
 \let\Textsize\normalsize
  \definecolor{DarkBlue}{rgb}{0.1,0.1,0.5}
  \definecolor{Red}{rgb}{0.9,0.0,0.1}
  %\def\Head#1{\noindent\hbox to \hsize{\hfil{\LARGE\color{DarkBlue} #1}}\bigskip}
  \def\LHead#1{\noindent{\LARGE\color{DarkBlue} #1}\smallskip}
  %\def\Subhead#1{\noindent{\large\color{DarkBlue} #1}}
  \def\Title#1{\noindent{\VeryHuge\color{Red} #1}}
  \renewcommand\texttt[1]{{\fontsize{20}{30}\ttfamily\selectfont #1}}
\fi
\def\strut{\vrule width 0pt height 0.7\baselineskip depth 0.3\baselineskip }
%\def\strut{\hrule width 0pt height 0.7\baselineskip depth 0.3\baselineskip }

\TPGrid[50mm,50mm]{11}{25} % width: 3x3 + 2x1 = 11

\parindent=0pt
\parskip=\baselineskip

\renewcommand\refname{\normalfont\LHead{References}}

\begin{document}
\Textsize
\raggedright


%% logos
\begin{textblock}{3}[1,1](11,25)
\begin{centering}
\hbox to\textwidth{\hss\GUlogo[width=0.8\textwidth]\hss}
\includegraphics[width=0.8\textwidth]{edinburgh-logo.png}\\[2cm]
\includegraphics[width=0.6\textwidth]{JISCcolour23.pdf}\\
\end{centering}
\end{textblock}

\begin{textblock}{11}(0,0)
\raggedleft
%\baselineskip=2\baselineskip
\Title{\strut The AstroDAbis Tagging Service:\\\strut tags and cross-matches for remote catalogues}\\
%\end{textblock}
%
%\begin{textblock}{16}(2,2)
%\def\ref#1{\raise1ex\hbox{\small #1}\hskip-0.05em}
\def\i#1{${}^{#1}$}
\LHead{\strut Norman Gray\i1, Robert G Mann\i2, Dave Morris\i3, Mark
  Holliman\i2 and Keith Noddle\i2\\
  \textsl{\strut \i1 School of Physics \& Astronomy, University of
    Glasgow, UK\\\strut \i2 WFAU, Institute for Astronomy, University of Edinburgh, UK\\\strut \i3 University of
    Bristol, UK}}
\end{textblock}

\begin{textblock}{3}(0,4)
\LHead{The short version}

% Title: 
%     Norman Gray (University of Glasgow, UK)
%     Robert G Mann (University of Edinburgh, UK)
%     Dave Morris (University of Bristol, UK)
%     Mark Holliman (University of Edinburgh, UK)
%     Keith Noddle (University of Edinburgh, UK)

% Poster abstract

Astronomers are very good at sharing data, but poorer at sharing knowledge.  The
AstroDAbis service helps share two types of knowledge:
\begin{itemize}
\item the results of, or input to, cross-matching algorithms, in the form of
    co-identifications or neighbour tables; and
\item information about single objects, in the form of user-supplied tags.
\end{itemize}

The majority of astronomical data ends up in open archives, and access to
these is being simplified by the development of the global Virtual
Observatory (VO).  This is a great advance, but the fundamental problem
remains that these archives contain only basic observational data, whereas
all the astrophysical interpretation of that data – which source is a
quasar, which a low-mass star, and which an image artefact – is contained
in journal papers, with very little linkage back from the literature to
the original data archives.  It is therefore currently impossible for
an astronomer to pose a query like “give me all sources in this data
archive that have been identified as quasars” and this limits the effective
exploitation of these archives, as the user of an archive has no direct
means of taking advantage of the knowledge derived by its previous users.

The AstroDAbis service aims to address this, in a prototype service
enabling astronomers to record tags and cross-identifications in the
AstroDAbis service, annotating objects in other catalogues.  We have
deployed two interfaces to the annotations, namely one astronomy-specific
one using the TAP protocol, and a second exploiting generic Linked Open
Data (LOD) and RDF techniques.

\end{textblock}

\begin{textblock}{7}(4,4)
\LHead{OGSA-DAI}

OGSA-DAI is an innovative solution for distributed data access and
management. It has been under development since 2002 and is now an
established open source product currently managed by EPCC, The
University of Edinburgh: \url{http://www.ogsadai.org.uk/}

\includegraphics[width=\textwidth]{../design/ogsadai-architecture.png}

In the configuration we are using, OGSA-DAI allows a user to run a
query across multiple TAP services.  The user submits an ADQL query to
a local TAP service, which that service translates into SQL for
submission to the OGSA-DAI server, which passes it on to a catalogue
server, and the AstroDAbis annotation server, as appropriate.

\end{textblock}

\begin{textblock}{3}(0,15)
\LHead{Input}
There are two ways to add tags to single objects.

The service supports a web-based interface, which allows a user to
enter templated queries (which expand to ADQL queries), tagging the
objects which result.

Alternatively (and more suitably for batch-mode or bulk annotation),
users can upload annotations contained in a VOTable
\begin{verbatim}
SELECT TOP 100 masterObjID as pts_key,
  slaveObjID as objID,
  distanceMins as tagvalue
FROM twomass_pscXBestDR7PhotoObjAll
  <FIELD name='pts_key ID='masterObjID'
      ucd='meta.id;meta.main' datatype='long'>
    <DESCRIPTION>
      The unique ID in twomass_psc (=pts_key)
    </DESCRIPTION>
  </FIELD>
  <FIELD name='objID' ID='slaveObjId'
      ucd='meta.id;meta.dataset'
      datatype='long'>
    <DESCRIPTION>
      The unique ID of the neighbour
      in BestDR7..PhotoObjAll (=objID)
    </DESCRIPTION>
  </FIELD>
  <FIELD name='tagvalue' ID='distanceMins' 
      ucd='pos.angDistance' datatype='float'
      unit='arcminutes' >
    <DESCRIPTION>
      Angular separation between neighbours
    </DESCRIPTION>
  </FIELD>
\end{verbatim}
\end{textblock}

\begin{textblock}{3}(8,15)
\LHead{Output}

Since the AstroDAbis service exposes a TAP interface to the world, its
annotation sets are available through ADQL interfaces such as the one
illustrated on the left.

The TAP interface makes the AstroDAbis a first-class citizen in the
VO, so that its users' annotations can be combined with information
from other VO services to support high-level queries such as, for
example, “find me the redshifts of all the objects which Fred Bloggs
identifies as quasars”.
\end{textblock}

\begin{textblock}{3}(4,15)
\LHead{Linked data and the Semantic Web}

As well as the TAP-based interface, AstroDAbis has a ‘Linked Data’
interface (see \url{http://linkeddata.org}).  Although this provides
utility by itself, it has the incidental feature that it provides a
mechanism for effectively creating URI-based \emph{names} for the
objects in the catalogues it annotates.  These can act as a
springboard for future experiments with the Semantic Web in astronomy.
\end{textblock}

\begin{textblock}{3}(4,18.5)
\LHead{Stand-off tagging}

A key feature of the AstroDAbis service is that it enables astronomer
users to annotate catalogues, and objects in catalogues, to which they
have no write access.  This creates the possibility of Web~2.0 or
Semantic Web infrastructures without requiring catalogues to make
the potentially disruptive changes to their systems which built-in
annotation would demand.

By providing a simple annotation service, the AstroDAbis mechanism
has the potential to support annotation of a very broad range of
astronomical objects, in a very broad range of repositories.
\end{textblock}

\begin{textblock}{3}[0,1](4,25)
\LHead{Links}
\begin{itemize}
\item \url{http://astrodabis.jiscinvolve.org}: canonical URL, but not
  much there
\item \url{http://astrodabis.googlecode.com}: code – includes documentation
  wiki (soon)
\end{itemize}
\end{textblock}

\begin{textblock}{3}(0,25.5)
{\fontsize{12}{16}\selectfont \HgNode, \HgDate}
\end{textblock}

\end{document}
